-
Notifications
You must be signed in to change notification settings - Fork 795
[CI] Move nightly SYCL benchmarking into a separate workflow #19280
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
Hi dpcpp-devops-reviewers, can I get some thoughts/opinions on what I'm doing here? If everyone is on-board with the changes being proposed here, we can go ahead with merging #19281 in order to test the changes being made here. |
…-benchmark-out-of-nightly
…-benchmark-out-of-nightly
Benchmark test runs:
As per Udit's suggestion, I switched the workflow to use Ubuntu 24.04 and that fixed the |
@intel/dpcpp-devops-reviewers Friendly ping, thanks!
|
@intel/llvm-gatekeepers PR is ready to merge, thanks! E2E errors are unrelated, as this PR does not touch anything outside of CI workflows files. |
Performance of SYCL has regressed a lot recently, causing nightly to fail consistently. However, if nightly is constantly failing, people may start to ignore nightly. #18766 should help with the amount of failures, but I am still figuring out the best parameters to use here, and additionally often times regressions are caused by driver changes, which is out of intel/llvm's control. Thus, for future's sake, it might be best to move benchmarking out of sycl-nightly.yml.
This PR moves nightly benchmarking into its own workflow/nightly job, 1hr before sycl-nightly.yml, in order to reduce the amount of failures in sycl nightly.